Computer wonks like to talk about garbage in/garbage out. A simple example: if there's a mistake in the way a blog post is encoded, many XML/RSS readers will choke on it, preventing all future posts from showing up.
The IT guys put up their hands and say, "well, if you hadn't had a lousy character, it wouldn't have broken... GIGO."
That's not resilient.
The work of the middleman is to inspect and recover. If your restaurant gets lousy fish from the boat, you don't get to serve it and proclaim garbage in garbage out. No, your job is to inspect what you get, and if necessary, change it.
If the school board gives the teacher lousy instructions, the teacher can easily put up his hands and say, "I'm just doing my job." The great teacher doesn't do that, of course. He provides a buffer between the administrators and the his real customers, the students.
There will always be garbage in. It's up to you as to whether or not there will be garbage out.
Today’s IT departments face an identity crisis. Technology is an integral part of every single business process, and has come to dominate the lives of consumers who are routinely shopping online, downloading information, and browsing the Internet.
Yet ironically, in an era when technology rules, IT departments are losing ground fast: The forces of cloud computing, social media, and information management are evolving rapidly, and business managers are discovering and adopting new technology before IT departments even have a chance to master it. Gartner Research predicts that by 2015, 35 percent of most companies’ technology-related expenditures will be managed outside the IT department’s budget.
In order to thrive and have an impact in today’s businesses, IT departments must stay relevant. They must become service-oriented organizations. That means deploying user-centric and agile solutions that meet the business needs of the organization and individual departments. That means delivering IT as a Service (ITaaS), and becoming a team of service-oriented experts.
The increased availability of Software as a Service applications (SaaS) makes it easy for individual departments to “go rogue” within an organization. Employees sign up for inexpensive outside-the-firewall public-cloud SaaS apps because they are convenient, easy-to-use, and address immediate needs – and because they believe they can meet their business needs better and faster than their IT department.
But users inevitably run into problems and end up going to IT for help. They may need to integrate the public-cloud application with another internal service, and/or import or export data. Then IT staff find themselves in an awkward position. They have to quickly master the application, understand the problem, and solve it. Along the way, they will likely identify risks associated with the use of this product – including critical security issues. Had they been involved right from the start, they could have provided real strategic value instead of simply putting out fires.
Likewise, developers are under the gun to conceive, prototype, and test applications, and then to get them into production. They often turn to public cloud providers for initial prototyping, testing, and even final deployment. The cloud offers a easy, self-service platform that developers can control and works the same across the development, testing, staging and live deployment phases. This practice relegates the IT department to the sidelines, and can minimize its value to that of maintaining legacy systems and infrastructure.
IT departments that remain passive legacy-system babysitters will be caught in a vicious cycle. Today, it is the CIO’s responsibility to bring awareness in the organization about the hidden dangers of decentralizing IT. There are four major ways to elevate IT’s role within the business, transforming it from being an old-school roadblock to a visionary service-oriented enabler:
This new service-oriented central IT model can deliver new benefits, including lower costs (by eliminating duplicate projects among different departments), more interoperability between differing SaaS applications, improved cohesion among departments, and reduced security risks.
Faster time to market for internal applications dramatically impacts the development side in an organization. An enterprise PaaS provides a common platform environment throughout the cycle and eliminates inconsistencies between development and final deployment. With PaaS, developers can now use the “right tool for the right job,” because any language and framework can be deployed in production.
Bart Copeland is CEO of ActiveState. You can read his blog posts here; follow him on Twitter @Bart_Copeland.
Have an idea for a post you’d like to contribute to GigaOm? Click here for our guidelines and contact info.
Photo courtesy aceshot1/Shutterstock.com.
Related research and analysis from GigaOM Pro:
Subscriber content. Sign up for a free trial.